Two Examples on How FDO Types can Support Machine and Human Readability

FAIR Digital Objects (FDOs) are typed by a well described set of attributes, where attributes key value pairs with key, which refers to syntactic description the value. Often is called also profile. The exact attribute keys obviously crucial for machine actionability on one hand. On other hand an can be way allow human readability used keys. Furthermore it often integrate legacy sets that provided inside repositories their digital objects. In following we show two examples FDO types from different viewpoints. are: Persistent Identifiers (PID) Instruments example and DARIAH (see https://de.dariah.eu) use case. both cases Handle system persistent identifiers, record PID found here as type-data in phrasing system. 1 Example 1: instrument goes back development kernel metadata, seen minimally required reference describe scientific instruments Stocker et al. 2020. space contains hierarchical objects lists attributes. An such definition single manufacturer occurs list manufacturers here: http://dtr-test.pidconsortium.eu/#objects/21.T11148/7adfcd13b3b01de0d875. 1.1. Record Full this case uses references definitions values, or full obtained Proxy https://hdl.handle.net/21.T11998/0000-001A-3905-1?noredirect structure defined type at ePIC Date Type Registry Schwardmann 2020 http://dtr-test.pidconsortium.eu/objects/21.T11148/17ce618137e697852ea6 . This refer qualified pair like TYPE/0.TYPE then names they given structure. becomes readable form without loosing any readability. For further details see: https://hdl.handle.net/21.T11998/0000-001A-3905-8?noredirect descriptions completely stored database service. itself metadata object its own. 1.2. PID4Inst based Attributes FDOs via proxy https://hdl.handle.net/21.T11148/17ce618137e697852ea6 DTR 1.3. Repository Another option store repositories. schema needed elements description. existing could bundled into complex definition, syntactically almost identical instruments. From derive repository entries. was directly derived type, conceptually definitions, but similar therefore exploitable same services. result derivation fed ingest module repositories, figure CORDRA types: https://hdl.handle.net/21.T11148/c2c8c452912d57a44117 https://vm11.pid.gwdg.de:8445/objects/21.11145/8fefa88dea40956037ec 2. 2: Use Case evolved humanities project about five years ago (Kálmán 2016, DARIAH-DE 2016). created far before records have been discussed. It provides relatively atomic values. humans expected: https://hdl.handle.net/21.11113/0000-000B-CA4C-D?noredirect does however not match goal Additionally has risk uncertainty ambiguity. 2.1. Attribute Definitions order make these readable, allowed spaces were data registries. basic information email address 'RESPONSIBLE' above instance: https://dtr-test.pidconsortium.eu/#objects/21.T11148/e117a4a29bfd07438c1e all registrie. able define records. 2.2. Legacy Records Such at: https://dtr-test.pidconsortium.eu/#objects/21.T11148/f1eea855587d8b1f66da If known repository, named very record. Usually previous would another FDO. require adaption repository. But since follow profile prefix, sufficient implement additional prefix level. Together rule lower level dominate higher level, makes out long time ago. 3. Presentation presentation will how supported discuss implementation infrastructure FAIRness more detail.